Mobile terminal and method of controlling a mobile terminal to display image upon receiving proximity touch input

ABSTRACT

A mobile terminal and a method of controlling a mobile terminal are provided. According to one embodiment, a mobile terminal includes: a touch screen for displaying and receiving information; and a controller for: controlling the touch screen to display a lock screen upon the mobile terminal entering a lock screen state; and controlling the touch screen to display a preview image of each of at least one application executed before entering the lock screen state upon receiving a proximity touch input on the displayed lock screen.

This application is a continuation of U.S. patent application Ser. No.13/029,070, filed on Feb. 16, 2011, currently pending, which claims thebenefit of earlier filing date and right of priority to Korean PatentApplication No. 10-2010-0095071 filed on Sep. 30, 2010, the contents ofwhich are all hereby incorporated by reference herein in their entirety.

FIELD OF THE INVENTION

Embodiments of the present invention relate to a mobile terminal and amethod of controlling a mobile terminal.

RELATED ART

Terminals can be divided into mobile terminals and stationary terminals.The mobile terminals can be classified as handheld terminals or vehiclemounted terminals according to whether users can personally carry theterminals.

In view of various types of services that are provided by mobileterminals, an improvement in the structure and/or software of mobileterminals is considered.

SUMMARY

Embodiments of the present invention relate to a mobile terminal and amethod of controlling a mobile terminal, and more particularly to amobile terminal (and a method of controlling a mobile terminal) forallowing a user to check required preview information and historyinformation without influence over a current state of the mobileterminal such that user convenience may be enhanced.

According to one embodiment, a mobile terminal includes: a touch screenfor displaying and receiving information; and a controller for:controlling the touch screen to display a lock screen upon the mobileterminal entering a lock screen state; and controlling the touch screento display a preview image of each of at least one application executedbefore entering the lock screen state upon receiving a proximity touchinput on the displayed lock screen.

According to one embodiment, a mobile terminal includes: a touch screenfor displaying and receiving information; and a controller forcontrolling the touch screen to display history information or previewinformation corresponding to a specific region of the touch screen uponreceiving a proximity touch input of the specific region.

According to one embodiment, a method of controlling a mobile terminalincludes: controlling a touch screen to display a lock screen upon themobile terminal entering a lock screen state; receiving a proximitytouch input via the displayed lock screen; and controlling the touchscreen to display a preview image of at least one application executedbefore entering the lock screen state on the displayed lock screen.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of described embodiments of the present invention and areincorporated in and constitute a part of this specification, illustrateembodiments of the present invention and together with the descriptionserve to explain aspects and features of the present invention.

FIG. 1 is a block diagram illustrating a configuration of a mobileterminal according to embodiments of the present invention;

FIGS. 2 and 3 are perspective views of a mobile terminal according toembodiments of the present invention.

FIG. 4 is a conceptual diagram for illustrating a proximity depth of aproximity sensor;

FIG. 5 is a flowchart illustrating a method of controlling a mobileterminal according to an embodiment of the present invention;

FIGS. 6A, 6B and 7A-7C are views of screen displays for illustratingexamples of displaying preview images of at least one application thatwas executed before entering a lock screen state based on a proximitytouch input;

FIGS. 8 to 12 are views of screen displays illustrating examples ofpreview images of an application in the lock screen state;

FIGS. 13A-13C, 14A, 14B, 15A-15C, 16A-16C, 17A-17D, 18A and 18B areviews of screen displays illustrating examples of ending the lock screenwhen preview images of an application are displayed on a locked screen;

FIG. 19 is a flowchart illustrating a method of controlling a mobileterminal according to another embodiment of the present invention;

FIGS. 20A, 20B, 21A-21D, 22A-22C, 23A-23C and 24A-24D are views ofscreen displays illustrating examples of displaying preview informationin a mobile terminal;

FIG. 25 is a flow chart illustrating a method of controlling a mobileterminal according to still another embodiment of the present invention;and

FIGS. 26A, 26B, 27A, 27B, 28A, 28B, 29A-29C, 30A, 30B and 31A-31D areviews illustrating of screen displays illustrating examples of historyinformation.

DETAILED DESCRIPTION

Embodiments of the present invention will now be described more fullywith reference to the accompanying drawings, in which certainembodiments of the invention are illustrated. The invention may,however, be embodied in many different forms and should not be construedas being limited to the embodiments set forth herein; rather, theseembodiments are described and/or illustrated so that this disclosurewill be more thorough and complete, and will more fully convey theaspects of the invention to those skilled in the art.

Hereinafter, a mobile terminal according to embodiments of the presentinvention will be described below in more detail with reference to theaccompanying drawings. In the following description, the suffixes“module” and “unit” are used in reference to components of the mobileterminal for convenience of description and do not have meanings orfunctions different from each other.

The mobile terminals described herein may include a cellular phone, asmart phone, a laptop computer, a digital broadcasting terminal, apersonal digital assistant (PDA), a portable multimedia player (PMP),and a navigation system.

FIG. 1 is a block diagram of a mobile terminal 100 according to anembodiment of the present invention. It is understood that otherembodiments, configurations and arrangements may also be provided. Withreference to FIG. 1, the mobile terminal 100 may include a wirelesscommunication unit 110, an audio/video (A/V) input unit 120, a userinput unit 130, a sensing unit 140, an output unit 150, a memory 160, aninterface unit 170, a controller 180, and a power supply 190. Not all ofthe components shown in FIG. 1 are essential, and the number ofcomponents included in the mobile terminal 100 may be varied. Thecomponents of the mobile terminal 100, as illustrated with reference toFIG. 1 will now be described.

The wireless communication unit 110 may include at least one module thatenables wireless communication between the mobile terminal 100 and awireless communication system or between the mobile terminal 100 and anetwork in which the mobile terminal 100 is located. For example, thewireless communication unit 110 may include a broadcast receiving module111, a mobile communication module 112, a wireless Internet module 113,a local area (or short-range) communication module 114, and a locationinformation (or position-location) module 115.

The broadcast receiving module 111 may receive broadcasting signalsand/or broadcasting related information from an external broadcastingmanagement server through a broadcasting channel. The broadcastingchannel may include a satellite channel and a terrestrial channel, andthe broadcasting management server may be a server that generates andtransmits broadcasting signals and/or broadcasting related informationor a server that receives previously created broadcasting signals and/orbroadcasting related information and transmits the broadcasting signalsand/or broadcasting related information to a terminal.

The broadcasting signals may include not only TV broadcasting signals,wireless broadcasting signals, and data broadcasting signals, but alsosignals in the form of a combination of a TV broadcasting signal and aradio broadcasting signal. The broadcasting related information may beinformation on a broadcasting channel, a broadcasting program or abroadcasting service provider, and may be provided even through a mobilecommunication network. In the latter case, the broadcasting relatedinformation may be received by the mobile communication module 112.

The broadcasting related information may exist in any of various forms.For example, the broadcasting related information may exist in the formof an electronic program guide (EPG) of a digital multimediabroadcasting (DMB) system or in the form of an electronic service guide(ESG) of a digital video broadcast-handheld (DVB-H) system.

The broadcast receiving module 111 may receive broadcasting signalsusing various broadcasting systems. More particularly, the broadcastreceiving module 111 may receive digital broadcasting signals usingdigital broadcasting systems such as a digital multimediabroadcasting-terrestrial (DMB-T) system, a digital multimediabroadcasting-satellite (DMB-S) system, a media forward link only(MediaFLO™) system, a DVB-H system, and an integrated services digitalbroadcast-terrestrial (ISDB-T) system. The broadcast receiving module111 may receive signals from broadcasting systems providing broadcastingsignals other than the above-described digital broadcasting systems.

The broadcasting signals and/or broadcasting related informationreceived through the broadcast receiving module 111 may be stored in thememory 160. The mobile communication module 112 may transmit/receive awireless signal to/from at least one of a base station, an externalterminal and a server on a mobile communication network. The wirelesssignal may include a voice call signal, a video call signal or data invarious forms according to the transmission and reception oftext/multimedia messages.

The wireless Internet module 113 may correspond to a module for wirelessInternet access and may be included in the mobile terminal 100 or may beexternally attached to the mobile terminal 100. Wireless LAN (WLAN orWi-Fi), wireless broadband (Wibro™) world interoperability for microwaveaccess (Wimax™), high speed downlink packet access (HSDPA) and othertechnologies may be used as a wireless Internet technique.

The local area communication module 114 may correspond to a module forlocal area communication. Further, Bluetooth™, radio frequencyidentification (RFID), infrared data association (IrDA), ultra wideband(UWB) and/or ZigBee™ may be used as a local area communicationtechnique.

The position-location module 115 may confirm or obtain the position ofthe mobile terminal 100. The position-location module 115 may obtainposition information by using a global navigation satellite system(GNSS). The GNSS refers to a radio navigation satellite system thatrevolves around the earth and transmits reference signals topredetermined types of radio navigation receivers such that the radionavigation receivers may determine their positions on the earth'ssurface or near the earth's surface. The GNSS may include a globalpositioning system (GPS) of the United States, Galileo of Europe, aglobal orbiting navigational satellite system (GLONASS) of Russia,COMPASS of China, and a quasi-zenith satellite system (QZSS) of Japanamong others.

A global positioning system (GPS) module is one example of theposition-location module 115. The GPS module 115 may calculateinformation regarding distances between one point or object and at leastthree satellites and information regarding a time when the distanceinformation is measured and apply trigonometry to the obtained distanceinformation to obtain three-dimensional position information on thepoint or object according to latitude, longitude and altitude at apredetermined time. A method of calculating position and timeinformation using three satellites and correcting the calculatedposition and time information using another satellite may also be used.In addition, the GPS module 115 may continuously calculate the currentposition in real time and calculate velocity information using thelocation or position information.

As shown in FIG. 1, the A/V input unit 120 may input an audio signal ora video signal and include a camera 121 and a microphone 122. The camera121 may process image frames of still images or moving pictures obtainedby an image sensor in a video call mode or a photographing mode. Theprocessed image frames may be displayed on a display module 151 whichmay be a touch screen.

The image frames processed by the camera 121 may be stored in the memory160 or may be transmitted to an external device through the wirelesscommunication unit 110. The mobile terminal 100 may also include atleast two cameras 121.

The microphone 122 may receive an external audio signal in a call mode,a recording mode or a speech recognition mode and process the receivedaudio signal into electronic audio data. The audio data may then beconverted into a form that may be transmitted to a mobile communicationbase station through the mobile communication module 112 and output inthe call mode. The microphone 122 may employ various noise removalalgorithms (or noise canceling algorithms) for removing or reducingnoise generated when the external audio signal is received.

The user input unit 130 may receive input data required for controllingthe mobile terminal 100 from a user. The user input unit 130 may includea keypad, a dome switch, a touch pad (e.g., constantvoltage/capacitance), a jog wheel, and a jog switch.

The sensing unit 140 may sense a current state of the mobile terminal100, such as an open/closed state of the mobile terminal 100, a positionof the mobile terminal 100, whether a user touches the mobile terminal100, a direction of the mobile terminal 100, andacceleration/deceleration of the mobile terminal 100, and generate asensing signal required for controlling the mobile terminal 100. Forexample, if the mobile terminal 100 is a slide phone, the sensing unit140 may sense whether the slide phone is opened or closed. Further, thesensing unit 140 may sense whether the power supply 190 supplies powerand/or whether the interface unit 170 is connected to an externaldevice. The sensing unit 140 may also include a proximity sensor 141.

The output unit 150 may generate visual, auditory and/or tactile outputand may include the display module 151, an audio output module 152, analarm unit 153 and a haptic module 154. The display module 151 maydisplay information processed by the mobile terminal 100. The displaymodule 151 may display a user interface (UI) or a graphic user interface(GUI) related to a voice call when the mobile terminal 100 is in thecall mode. The display module 151 may also display a captured and/orreceived image and a UI or a GUI when the mobile terminal 100 is in thevideo call mode or the photographing mode.

In addition, the display module 151 may include at least a liquidcrystal display, a thin film transistor liquid crystal display, anorganic light-emitting diode display, a flexible display or athree-dimensional display. Some of these displays may be of atransparent type or a light transmissive type. That is, the displaymodule 151 may include a transparent display.

The transparent display may include a transparent liquid crystaldisplay. The rear of the display module 151 may include a lighttransmissive type display. Accordingly, a user may be able to see anobject located behind the body of the mobile terminal 100 through thetransparent portion of the display unit 151 on the body of the mobileterminal 100.

The mobile terminal 100 may also include at least two display modules151. For example, the mobile terminal 100 may include a plurality ofdisplay modules 151 that are arranged on a single face of the mobileterminal 100 and spaced apart from each other at a predetermineddistance or that are integrated together. The plurality of displaymodules 151 may also be arranged on different sides of the mobileterminal 100.

Further, when the display module 151 and a touch-sensing sensor(hereafter referred to as a touch sensor) form a layered structure thatis referred to as a touch screen, the display module 151 may be used asan input device in addition to an output device. The touch sensor may bein the form of a touch film, a touch sheet, or a touch pad, for example.

The touch sensor may convert a variation in pressure, applied to aspecific portion of the display module 151, or a variation incapacitance, generated at a specific portion of the display module 151,into an electric input signal. The touch sensor may sense pressure,position, and an area (or size) of the touch.

When the user applies a touch input to the touch sensor, a signalcorresponding to the touch input may be transmitted to a touchcontroller. The touch controller may then process the signal andtransmit data corresponding to the processed signal to the controller180. Accordingly, the controller 180 may detect a touched portion of thedisplay module 151.

The proximity sensor 141 of the sensing unit 140 may be located in aninternal region of the mobile terminal 100, surrounded by the touchscreen, or near the touch screen. The proximity sensor 141 may sense thepresence of an object approaching a predetermined sensing face or anobject located near the proximity sensor using an electromagnetic forceor infrared rays without mechanical contact. The proximity sensor 141may have a lifetime longer than a contact sensor and may thus be moreappropriate for use in the mobile terminal 100.

The proximity sensor 141 may include a transmission type photoelectricsensor, a direct reflection type photoelectric sensor, a mirrorreflection type photoelectric sensor, a high-frequency oscillatingproximity sensor, a capacitive proximity sensor, a magnetic proximitysensor, and/or an infrared proximity sensor. Meanwhile, a capacitivetouch screen may be constructed such that proximity of a pointer isdetected through a variation in an electric field according to theproximity of the pointer. Therefore, the touch screen (touch sensor) maybe considered as a proximity sensor 141 if the touch screen isimplemented as the capacitive touch screen.

For the convenience of description, an action in which a pointerapproaches the touch screen without actually touching the touch screenmay be referred to as a proximity touch, and an action in which thepointer is brought into contact with the touch screen may be referred toas a contact touch. The proximity touch point of the pointer on thetouch screen may correspond to a point of the touch screen at which thepointer is perpendicular to the touch screen.

The proximity sensor 141 may sense the proximity touch and a proximitytouch pattern (e.g., a proximity touch distance, a proximity touchdirection, a proximity touch velocity, a proximity touch time, aproximity touch position, a proximity touch moving state). Informationcorresponding to the sensed proximity touch action and proximity touchpattern may then be displayed on the touch screen.

The audio output module 152 may output audio data received from thewireless communication unit 110 or stored in the memory 160 in a callsignal receiving mode, a call mode or a recording mode, a speechrecognition mode and a broadcast receiving mode. The audio output module152 may output audio signals related to functions performed in themobile terminal 100, such as a call signal incoming tone and a messageincoming tone. The audio output module 152 may include a receiver, aspeaker, and/or a buzzer. The audio output module 152 may output soundsthrough an earphone jack. The user may listen to the sounds byconnecting an earphone to the earphone jack.

The alarm unit 153 may output a signal indicating generation (oroccurrence) of an event of the mobile terminal 100. For example, alarmsmay be generated when a call signal or a message is received and when akey signal or a touch is input. The alarm unit 153 may also outputsignals different from video signals or audio signals, for example, asignal indicating generation of an event through vibration. The videosignals or the audio signals may also be output through the displaymodule 151 or the audio output module 152.

The haptic module 154 may generate various haptic effects that the usermay feel. One of the haptic effects is vibration. The intensity and/orpattern of a vibration generated by the haptic module 154 may also becontrolled. For example, different vibrations may be combined with eachother and output or may be sequentially output.

The haptic module 154 may generate a variety of haptic effects includingan effect attributed to an arrangement of pins vertically moving againsta contact skin surface, an effect attributed to a jet force or asuctioning force of air through a jet hole or a suction hole, an effectattributed to a rubbing of the skin, an effect attributed to contactwith an electrode, an effect of stimulus attributed to an electrostaticforce, and an effect attributed to a reproduction of cold and warmthusing an element for absorbing or radiating heat in addition tovibrations.

The haptic module 154 may not only transmit haptic effects throughdirect contact but may also allow the user to feel haptic effectsthrough the user's fingers or arms. The mobile terminal 100 may alsoinclude a plurality of haptic modules 154.

The memory 160 may store a program for operating the controller 180 andtemporarily store input/output data such as a phone book, messages,still images, and/or moving pictures. The memory 160 may also store dataregarding various patterns of vibrations and sounds that are output fromwhen a touch input is applied to the touch screen.

The memory 160 may include at least a flash memory, a hard disk typememory, a multimedia card micro type memory, a card type memory such asSD or XD memory, a random access memory (RAM), a static RAM (SRAM), aread-only memory (ROM), an electrically erasable programmable ROM(EEPROM), a programmable ROM (PROM) magnetic memory, a magnetic disk, oran optical disk. The mobile terminal 100 may also operate in associationwith a web storage performing the storage function of the memory 160 onthe Internet.

The interface unit 170 may serve as a path to external devices connectedto the mobile terminal 100. The interface unit 170 may receive data orpower from the external devices, transmit the data or power to internalcomponents of the mobile terminal 100, or transmit data of the mobileterminal 100 to the external devices. For example, the interface unit170 may include a wired/wireless headset port, an external charger port,a wired/wireless data port, a memory card port, a port for connecting adevice having a user identification module, an audio I/O port, a videoI/O port, and/or an earphone port.

The interface unit 170 may also interface with a user identificationmodule that is a chip that stores information for authenticatingauthority to use the mobile terminal 100. For example, the useridentification module may be a user identity module (UIM), a subscriberidentity module (SIM) and a universal subscriber identify module (USIM).An identification device including the user identification module mayalso be manufactured in the form of a smart card. Accordingly, theidentification device may be connected to the mobile terminal 100through a port of the interface unit 170.

The interface unit 170 may also be a path through which power from anexternal cradle is provided to the mobile terminal 100 when the mobileterminal 100 is connected to the external cradle or a path through whichvarious command signals input by the user through the cradle areprovided to the mobile terminal 100. The various command signals orpower input from the cradle may be used as signals for checking whetherthe mobile terminal 100 is correctly settled (or loaded) in the cradle.

The controller 180 may control overall operations of the mobile terminal100. For example, the controller 180 may control and process voicecommunication, data communication and/or a video call. The controller180 may also include a multimedia module 181 for playing a multimediafile. The multimedia module 181 may be included in the controller 180 asshown in FIG. 1 or may be separated from the controller 180.

The controller 180 may perform a pattern recognition process ofrecognizing handwriting input or picture-drawing input applied to thetouch screen as characters or images. The power supply 190 may receiveexternal power and internal power and provide power required foroperating the components of the mobile terminal 100 under the control ofthe controller 180.

According to a hardware implementation, embodiments of the presentinvention may be implemented using at least application specificintegrated circuits (ASICs), digital signal processors (DSPs), digitalsignal processing devices (DSPDs), programmable logic devices (PLDs),field programmable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, and/or electrical units forexecuting functions. The embodiments may be implemented using thecontroller 180.

According to a software implementation, embodiments including proceduresor functions may be implemented using a separate software moduleexecuting at least one function or operation. Software code may beimplemented according to a software application written in anappropriate software language. The software codes may be stored in thememory 160 and executed by the controller 180.

FIG. 2 is a front perspective view of a mobile terminal or a handheldterminal 100 according to an embodiment of the present invention. Thehandheld terminal 100 has a bar type terminal body. However, embodimentsof the present invention are not limited to a bar type terminal and mayinclude various types of terminals such as slide type, folder type,swing type and swivel type terminals having at least two bodies coupledsuch that they can move relative to each other.

The terminal body includes a case (a casing, a housing, or a cover)forming the exterior of the terminal 100. In the embodiment of FIG. 2,the case may be divided into a front case 101 and a rear case 102.Various electronic components are arranged in the space (volume) definedbetween the front case 101 and the rear case 102. At least one middlecase may be additionally arranged between the front case 101 and therear case 102. The cases may be made of plastics through injectionmolding or made of a metal material such as stainless steel (STS) ortitanium (Ti).

The display module 151, the audio output module 152, the camera 121,user input unit 130 (e.g., operating units 131, 132), the microphone 122and the interface unit 170 may be arranged in the terminal body,specifically, in the front case 101.

The display module 151 occupies a majority of the area of the main faceof the front case 101. The audio output module 152 and the camera 121are arranged in a region in proximity to an end of the display module151, and the operating unit 131 and the microphone 122 are located in aregion in proximity to the other end of the display module 151. Theoperating unit 132 and the interface unit 170 are arranged on thelateral sides of the front case 101 and the rear case 102.

The user input unit 130 is operated to receive commands controlling thehandheld terminal 100 and may include a plurality of operating units 131and 132. The first and second operating units 131 and 132 may bereferred to as manipulating portions and may employ a tactile mechanismby which a user operates the operating units 131 and 132 by touch.

The first and second operating units 131 and 132 may receive variousinputs. For example, the first operating unit 131 receives commands suchas ‘START,’ END,' and ‘SCROLL,’ and the second operating unit 132receives commands such as ‘CONTROL’ (the volume of sound output from theaudio output module 152) or ‘CONVERT’ (a mode of the display module 151into a touch recognition mode).

FIG. 3 is a rear perspective view of the handheld terminal shown in FIG.2 according to an embodiment of the present invention.

Referring to FIG. 3, a camera 121′ may be additionally mounted at therear side of the terminal body, that is, the rear case 102. The camera121′ captures images along a direction opposite to that of the camera121 shown in FIG. 2 and may have a pixel resolution different from thatof the camera 121.

For example, according to one embodiment, the camera 121 has arelatively low resolution suitable for capturing an image of the face ofa user and transmitting the captured image in a video call, while thecamera 121′ has a relatively high resolution suitable for capturing aphotograph of a general subject. The cameras 121 and 121′ may be mountedto the terminal body such that they may be rotated or popped-up.

A flash 123 and a mirror 124 may be additionally arranged in proximityto the camera 121′. The flash 123 lights a subject when the camera 121′takes a picture of the subject. The mirror 124 may be used by the userto view his/her face when the user wants to self-photographhimself/herself using the camera 121′.

An audio output module 152′ may be additionally provided on the rearside of the terminal body. The audio output module 152′ may facilitate astereo function in conjunction with the audio output module 152 shown inFIG. 2 and may be used in a speaker phone mode when the terminal is usedfor a voice call.

A broadcasting signal receiving antenna 116 may be additionally attachedto the side of the terminal body in addition to an antenna for voicecalls. The antenna, which may constitute a part of the broadcastreceiving module 111 shown in FIG. 1, may be mounted in the terminalbody such that the antenna may be pulled out from (and retracted into)the terminal body.

The power supply 190 for providing power to the handheld terminal 100 isset in the terminal body. The power supply 190 may be provided in theterminal body or detachably installed on the terminal body.

A touch pad 135 for sensing a touch may be additionally attached to therear case 102. The touch pad 135 may be of a light transmission typesimilar to the display module 151. In this configuration, if the displaymodule 151 outputs visual information through both of its sides (orfaces), the visual information may be viewable via the touch pad 135.The information output through both sides of the display unit 151 may becontrolled by the touch pad 135. Alternatively (or in addition), adisplay is additionally attached to the touch pad 135 such that a touchscreen may be arranged in the rear case 102.

The touch pad 135 operates in connection with the display module 151 ofthe front case 101. The touch pad 135 may extend parallel to the displaymodule 151 behind the display module 151. The touch panel 135 may have asize equal to or smaller than the size of the display module 151.

FIG. 4 is a conceptual diagram for explaining a proximity depth of theproximity sensor. Referring to FIG. 4, when a pointer such as a user'sfinger approaches the touch screen 151, the proximity sensor locatedinside or near the touch screen senses the approach and outputs aproximity signal. The proximity sensor may be configured to output aproximity signal according to the distance between the pointerapproaching the touch screen and the touch screen (referred to as a“proximity depth”).

The distance, according to which the proximity signal is output when thepointer approaches the touch screen, is referred to as a detectiondistance. The proximity depth may be detected by using a plurality ofproximity sensors having different detection distances and by comparingrespective proximity signals output from the proximity sensors.Referring to FIG. 4, proximity sensors for sensing three proximitydepths are arranged in a section of the touch screen. Alternatively,proximity sensors suitable for sensing less than three proximity depthsor more than four proximity depths may be arranged in the touch screen.

Referring to FIG. 4, when the pointer comes into contact (e.g., completecontact) with the touch screen (distance of DO), it is recognized as acontact touch. When the pointer is located within a distance D1 from thetouch screen, it is recognized as a proximity touch of a first proximitydepth. When the pointer is located in a range between the distance D1and a distance D2 from the touch screen, it is recognized as a proximitytouch of a second proximity depth. When the pointer is located in arange between the distance D2 and a distance D3 from the touch screen,it is recognized as a proximity touch of a third proximity depth. Whenthe pointer is located at a position further than the distance D3 fromthe touch screen, no proximity touch or a cancellation (e.g.,termination) of a proximity touch is recognized.

Accordingly, the controller 180 may recognize the proximity touch asvarious input signals according to the proximity distance and theproximity position of the pointer with respect to the touch screen. Thecontroller 180 may perform various control operations according to theinput signals.

Embodiments of the present invention may be implemented in the mobileterminal(s) 100 described with reference to FIGS. 1 to 4. Hereinafter, amethod of controlling the mobile terminal 100 according to embodimentsof the present invention and operation of the mobile terminal 100performing the method will be described in more detail with reference toFIGS. 5, 6A, 6B, 7A-7C, 8-12, 13A-13C, 14A, 14B, 15A-15C, 16A-16C,17A-17D, 18A and 18B.

FIG. 5 is a flowchart of a method of controlling the mobile terminal 100according to an embodiment of the present invention. FIGS. 6A, 6B,7A-7C, 8-12, 13A-13C, 14A, 14B, 15A-15C, 16A-16C, 17A-17D, 18A and 18Bare views of display screens illustrating the method of controlling themobile terminal 100 according to embodiments of the present invention.

Referring to FIG. 5, the controller 180 enters a lock screen state anddisplays a lock screen on the touch screen 151 indicating that themobile terminal 100 has entered the lock screen state (S101). The lockscreen function is for preventing the mobile terminal 100 from beingoperated when an undesired touch input occurs on the touch screen 151.According to an embodiment of the present invention, the controller 180performs a function corresponding to a specific touch input incontrolling the mobile terminal 100 to enter the lock screen state. Forexample, the controller 180 enters the lock screen state when the entryinto the lock screen state is requested through the user input unit 130or when a control input is not received over a predetermined time.

When the touch screen 151 is proximity-touched and the proximity touchinput is received (S102), the controller 180 displays a preview image(or preview information) of at least one application on the touch screen151 based on the received proximity touch input (S103). For example, theat least one application for which the preview image is displayed may bean application that was being executed before the mobile terminal 100entered the lock screen state.

In the operation S102, the proximity touch input that triggers thedisplay of the preview image of the at least one application in the lockscreen state may be input (or generated in various manners as describedbelow. FIGS. 6A, 6B, 7A, 7B and 7C are views of screen displaysillustrating examples of the display of preview images of at least oneapplication based on the proximity touch input, where the at least oneapplication was being executed before entry into the lock screen state.

The controller 180 may display the preview image of the application whenat least one point of the touch screen 151 is proximity-touched when themobile terminal 100 is in the lock screen state. Referring to FIG. 6A,the controller 180 receives the proximity touch input through the touchscreen on which a lock screen 5 is displayed.

Referring to FIG. 6B, the controller 180 then displays a preview image 6a of an application, for example, of a gallery application that wasbeing executed before the mobile terminal 100 entered the lock screenstate. The controller 180 displays (or causes the touch screen 151 todisplay) the preview image 6 a such that the preview image 6 a overlapswith the lock screen 5 on a portion of the touch screen 151. That is,the preview image 6 a is superimposed over the lock screen 5 on aportion of the touch screen. As illustrated in FIG. 6B, the previewimage 6 a includes an execution screen of the gallery application.

In addition, the controller 180 may display a preview image of anapplication on the touch screen 151 when a specific region of the touchscreen 151 is selected and dragged by a proximity touch. Referring toFIG. 7A, the controller 180 displays a slide type lock release region 7a, which may be dragged on the lock screen 5. The lock release region 7a is for receiving a touch input for ending (or exiting) the lock screenstate. Referring to FIG. 7B, the lock release region 7 a is touched by aproximity touch.

Referring to FIG. 7C, the controller 180 displays the preview image 6 aof the application that was being executed before the lock screen statewas entered when the lock release region 7 a is dragged toward an upperend of the screen. In this situation, the controller 180 may steadily(e.g., incrementally) move the display of the lock release region 7 atoward the upper end of the screen based on the drag path of theproximity touch. The controller 180 may display the preview image 6 a ata location from which the lock release region 7 a is dragged and movedas the display of the lock release region 7 a is moved upwards. Further,the display region of the preview image 6 a may be expanded as the lockrelease region 7 a is further dragged toward the upper end of thescreen.

For example, the controller 180 may increase a size of the executionscreen of the application included in the preview image 6 a as thedisplay region of the preview image 6 a is expanded. To this end, thecontroller 180 may match the display region of the preview image 6 a toa region of the execution screen of the application and may display theregion of the execution screen of the application that is matched to thedisplay region of the preview image 6 a in the preview image 6 a. Inaddition, the controller 180 may expand (or enlarge) the displayedpreview image 6 a (relative to the initially displayed preview image 6a) as the display region of the preview image 6 a is expanded.

In the operation of S103 (see FIG. 5), the controller 180 may generate apreview image of an application in various manners as will be describedin more detail below. FIGS. 8 to 12 are views of screen displaysillustrating examples of a preview image of an application that isdisplayed when the mobile terminal 100 is in the lock screen state.

The controller 180 may generate a preview image to include some regionof the execution screen of the application. In more detail, when anentry into the lock screen state is requested, the controller 180 storesa final execution screen (e.g., a screen snapshot) of the applicationthat is being executed in the memory 160. At least a portion of thefinal execution screen stored in the memory 160 may be used as a previewimage of a corresponding application.

Referring to FIG. 8, when the mobile terminal 100 enters the lock screenstate while a gallery application displays an image list (or series ofimages), the controller 180 displays a portion of the image list (whichwas displayed directly before the entry into the lock screen state) asthe preview image 6 a on the lock screen 5. Referring to FIG. 9, whenthe mobile terminal 100 enters the lock screen state while apredetermined application displays a calendar image, the controller 180displays a reduced (or shrunken) image of the calendar image (which wasdisplayed directly before the entry into the lock screen state) as apreview image 6 a on the lock screen 5.

As illustrated in FIG. 8, when the preview image 6 a is displayed usinga portion of the execution screen of the application according to aproximity touch of at least one point of the touch screen 151, thecontroller 180 may display different preview images according to thepoint of the touch screen 151 that is proximity-touched. In more detail,when a specific point of the touch screen 151 is proximity-touched, thecontroller 180 matches the proximity-touched point to (a correspondinglypositioned portion of) the final execution screen of the applicationthat was being executed before the entry into the lock screen state. Inaddition, the controller 180 displays the corresponding portion of thefinal execution screen of the application as a preview image based onthe matched location of the proximity-touched point.

When the mobile terminal 100 is operating in a multi-tasking mode beforethe entry into the lock screen state, the controller 180 may display allof a plurality of executing screens of applications that were beingexecuted as preview images. Referring to FIG. 10, the controller 180displays preview images 6 a, 6 a′, and 6 a″ by reducing (or shrinking)respective execution screens of a scheduling application, a contactsapplication, and a music reproducing application that were beingexecuted in the multi-tasking mode before the entry into the lock screenstate. In addition, referring to FIG. 11, when the lock release region 7a is selected and dragged upwards, the controller 180 displays at leastportions of the execution screens of the scheduling, contacts, and musicreproducing applications (which were being executed in the multi-taskingmode before the entry into the lock screen state) as preview images 6 a,6 a′, and 6 a″. The controller 180 may increase portions of theexecution screens displayed as the preview images 6 a, 6 a′, and 6 a″ asthe sizes of the displayed preview images 6 a, 6 a′, and 6 a″ areincreased as the lock release region 7 a is progressively draggedupwards by the proximity touch.

When the mobile terminal 100 has usage restrictions or when access of anapplication that was being executed before the entry into the lockscreen state is restricted, the controller 180 may display at least aportion of a password input screen as a preview image instead of theexecution screen of the application. Referring to FIG. 12, thecontroller 180 displays a portion of a password input screen (instead ofthe execution screen of the application) as the preview image 6 a. Thepreview image 6 a overlaps the lock screen 5.

Referring back to FIG. 5, if ending of (or exit out of) the lock screenstate is requested when a preview image of a previously executedapplication is displayed (S104), the controller 180 ends (or controlsthe mobile terminal 100 to exit) the lock screen state (S105). In theoperation of S104, an input requesting ending of the lock screen statemay be received in various manners as described below. FIGS. 13A-13C,14A, 14B, 15A-15C, 16A-16C, 17A-17D, 18A and 18B are views of screendisplays illustrating examples of ending the lock screen state whenpreview images of an application are displayed on a locked screen.

The controller 180 may end the lock screen state when the preview imagethat is displayed in the lock screen state is contacted and touched.Referring to FIG. 13A, the controller 180 displays a plurality ofpreview images 6 a, 6 a′, and 6 a″ corresponding to applications thatwere being executed before the entry into the lock screen state. Withcontinued reference to FIG. 13A, the lock screen 5 is proximity-touched.Consequently, referring to FIG. 13B, the controller 180 ends the lockscreen state when any one of the preview images 6 a, 6 a′, and 6 a″ thatare displayed on the screen is contacted and touched. Referring to FIG.13C, the controller 180 executes the application(s) that was beingexecuted before the entry into the lock screen state and enters anapplication corresponding to the contacted and touched preview image.That is, the controller 180 displays an execution screen of anapplication corresponding to the preview image that was contacted andtouched on the touch screen 151.

In more detail, the controller 180 stores a final entry step (oroperation) of at least one application that is being executed beforeentering the lock screen state in the memory 160. When the applicationis executed again at the ending of the lock screen state, the controller180 executes the application from the state that it was in before theentry into the lock screen state based on the final entry step that isstored in the memory 160. Referring to FIG. 14A, the controller 180 endsthe lock screen state when a specific item 14 a included in the previewimage 6 a is contacted and touched. In addition, the controller 180re-executes (or again executes) a corresponding application and executesan application function related to the contacted and touched specificitem 14 a. For example, with reference to FIGS. 14A and 14B, when acalendar screen of a predetermined application is displayed in a previewimage 6 a in the lock screen state and when a specific item 14 acorresponding to the schedule of a particular day is contacted andtouched, the controller 180 displays detailed information 14 of thecorresponding schedule on the screen.

When a specific portion of the lock screen is dragged longer (orfarther) than a predetermined distance by the proximity touch, thecontroller 180 may end the lock screen state. Referring to FIG. 15A, thecontroller 180 displays the preview image 6 a of the previously executedapplication on the screen when a specific region, for example, the lockrelease region 7 a, of the lock screen is dragged by proximity touch.Referring to FIG. 15B, the controller 180 ends the lock screen statewhen the lock release region 7 a is dragged farther than a predetermineddistance. Consequently, referring to FIG. 15C, the controller 180re-executes an application corresponding to the preview image 6 a. Thatis, the controller 180 displays the execution screen 15 of theapplication corresponding to the preview image 6 a on the touch screen151.

The controller 180 may end the lock screen state when the preview imageof the application displayed on the lock screen is dragged into aspecific region by the proximity touch. Referring to FIG. 16A, thecontroller 180 displays the preview image 6 a of the application thatwas being executed before the entry into the lock screen state when thelock screen 5 is proximity-touched. The preview image 6 a is selected bya proximity touch. Referring to FIG. 16B, the controller 180 ends thelock screen state when the preview image 6 a is dragged into a specificregion of the lock screen 5, for example, a lock release button region16 a, by the proximity touch. Consequently, referring to FIG. 16C, thecontroller 180 displays an execution screen of the applicationcorresponding to the dragged preview image 6 a. That is, the controller180 displays an execution screen 16 of the application corresponding tothe preview image 6 a on the touch screen 151.

The controller 180 may end the lock screen state when a size of thepreview image displayed on the lock screen is increased to become largerthan a predetermined size based on a multi-touch input by a proximitytouch. Referring to FIG. 17A, the controller 180 displays the previewimage 6 a of the application that was being executed before the entryinto the lock screen state when the lock screen 5 is proximity-touched.The preview image 6 a is selected by a proximity touch. Referring toFIG. 17B, the controller 180 changes the size of the displayed previewimage 6 a when the preview image 6 a is touched again by the proximitytouch and when a drag input that starts from at least one point isreceived via the proximity touch.

Referring to FIGS. 17C and 17D, the controller 180 ends the lock screenstate when the size of the displayed preview image 6 a is increased tobecome larger than a predetermined size. In addition, referring to FIG.17D, the controller 180 re-executes an application that was beingexecuted before the entry into the lock screen state. That is, thecontroller 180 displays an execution screen 17 of an applicationcorresponding to the preview image 6 a on the touch screen 151.

In the operation of S105 (see FIG. 5), when the lock screen state isended as illustrated in FIGS. 13C, 14B, 15C, 16C and 17D, the controller180 re-executes at least one of the applications that was being executedbefore the entry into the lock screen state and displays an executionscreen of the at least one of the re-executed applications on the touchscreen 151. However, in a situation where the mobile terminal 100 has ausage restriction or where access to the application that was beingexecuted before the entry into the lock screen state is restricted, thecontroller 180 may display a password input screen instead of theexecution screen of the application when the lock screen state is ended.

Referring to FIG. 18A, the controller 180 displays a portion of thepassword input screen as a preview image 6 a overlapping with the lockscreen 5, instead of a portion of the execution screen of theapplication. Subsequently, referring to FIG. 18B, when the lock screenstate is ended, the controller 180 displays the password input screen 18on the screen.

According to previously-described embodiments of the present invention,it is possible for a user to check a previously executed application inadvance using the proximity touch without ending the lock screen state.Moreover, it is also possible for a user to check an applicationexecuted before the lock screen state was entered and to proceed towardrequesting an ending of the lock screen state without a break. Inaddition, when the mobile terminal 100 has a usage restricted or whenaccess to the application that was being executed before the entry intothe lock screen state is restricted, the controller 180 may display thepassword input screen as a preview image instead of the execution screenof the application so that user convenience is enhanced and privacyprotection is reinforced.

Hereinafter, a method of controlling a mobile terminal 100 according toother embodiments of the present invention and operation of the mobileterminal for performing the method will be described in more detail withreference to FIGS. 19, 20A, 20B, 21A-21D, 22A-22C, 23A-23C and 24A-24D.

FIG. 19 is a flowchart illustrating a method of controlling a mobileterminal according to another embodiment of the present invention. FIGS.20A, 20B, 21A-21D, 22A-22C, 23A-23C and 24A-24D are views of screendisplays illustrating the method according to embodiments of the presentinvention.

Referring to FIG. 19, the controller 180 receives a proximity touchinput on the touch screen 151 (S1001). When there is preview informationcorresponding to a region where the proximity touch occurs (S1002), thecontroller 180 displays the corresponding preview information on thetouch screen 151 (S1003). Regarding the operation of S1003, differentpreview information may be selected based on an operation mode of themobile terminal 100, a function of an application that is currentlyexecuted, and an item displayed on the region where the proximity touchoccurs.

FIGS. 20A, 20B, 21A-21C, 22A-22C, 23A-23C, 24A-24D and 25 show examplesof screen displays displaying preview information in the mobile terminal100. The controller 180 may display preview information regarding alarminformation when the alarm information is proximity-touched while themobile terminal 100 is operating in the lock screen state. The alarminformation includes information of which a user is to be notified suchas a missed call, an unchecked received message, and a schedule.

Referring to FIG. 20A, while the mobile terminal 100 is operating in thelock screen state, the controller 180 displays alarm information 20 aand 20 b for notifying the user of a missed voice call and a missedvideo call, respectively, and alarm information 20 c for notifying theuser of a particular schedule (e.g., today's schedule) on the lockscreen 5. As illustrated with reference to FIG. 20A, among the alarminformation 20 a, 20 b and 20 c that is displayed on the lock screen 5,the alarm information 20 a for notifying the user of a missed voice callnumber is proximity-touched (S1101). Subsequently, referring to FIG.20B, the controller 180 displays preview information 20 d correspondingto the missed calls on the lock screen 5. When the displayed previewinformation 20 d is contacted and touched, the controller 180 may endthe lock screen state and display more detailed informationcorresponding to the contacted-and-touched preview information 20 d onthe screen.

When a specific region of a message writing screen is proximity-touchedduring the writing (or creation) of a message, the controller 180 maydisplay preview information (e.g., a preview) of the in-progress messageon the screen.

Referring to FIG. 21A, the controller 180 displays a message writingscreen 21 on the touch screen 151. Referring to FIG. 21B, when aspecific region of the message writing screen 21, for example, a regionwhere a send button 21 a is displayed, is proximity-touched, thecontroller 180 displays preview information 21 b of the message that isbeing written. That is, the controller 180 displays a preview image ofthe current message on the screen. The controller 180 may activate orterminate display of the preview information according to a proximitytouch depth of the send button 21 a.

For example, referring to FIG. 21C, when a distance between a pointercausing the proximity touch (e.g., the user's finger) and the touchscreen 151 becomes shorter than a predetermined distance, the controller180 deletes the preview information 21 b displayed on the screen.Further, referring to FIG. 21D, when the send button 21 a is contactedand touched, the controller 180 executes a send function, which is aninherent function mapped (or corresponding) to the send button 21 a.That is, the controller 180 transmits the current written message to adesignated recipient.

For example, with reference back to FIG. 4, the controller 180 activatesthe displaying of the preview information 21 b when a distance betweenthe pointer and the touch screen 151 is within a range from D1 to D3(e.g., a range from greater than or equal to D1 to less than or equal toD3). When the distance between the pointer and the touch screen 151becomes shorter than D1, the controller 180 inactivates (or terminates)the displaying of the preview information 21 b. In addition, when thedistance between the pointer and the touch screen 151 is reduced to D0,that is, when the send button 21 a displayed on the touch screen 151 isdirectly contacted and touched, the controller 180 executes an inherentfunction mapped to the send button 21 a.

The controller 180 may display preview information (e.g., a preview) ofa photographed image when a specific region of a photographing screen isproximity-touched while the mobile terminal 100 is operating in aphotographing mode. That is, the controller 180 displays a photographedimage of an external view that is input through the camera 121 as apreview image.

Referring to FIG. 22A, the controller 180 displays a photographed image22 on the screen when the mobile terminal 100 enters the photographingmode. When a specific region of the photographing screen 22, forexample, a photograph button 22 a is proximity-touched, the controller180 displays an image generated by photographing an external view thatis input through the camera 121 as preview information 22 b. That is,the controller 180 displays a preview image, generated by photographingan external view that is currently input through the camera 121, on thescreen.

The controller 180 may activate or inactivate the displaying of thepreview information 22 b according to the proximity touch depth withrespect to the photograph button 22 a. For example, referring to FIG.22B, the controller 180 inactivates the displaying of the previewinformation 22 b when the proximity touch depth of the photograph button22 a becomes shorter than a predetermined distance. In addition,referring to FIG. 22C, the controller 180 executes a photographingfunction (an inherent function mapped (or corresponding) to thephotograph button 22 a) when the photograph button 22 a is contacted andtouched. That is, the controller 180 photographs an external view inputthrough the camera 121 and stores the photographed image in the memory160.

For example, with reference back to FIG. 4, when a distance between apointer causing the proximity touch (e.g., the user's finger) and thetouch screen 151 is within a range from D1 to D3, the controller 180activates the displaying of the preview information 22 b. When thedistance between the pointer and the touch screen 151 becomes shorterthan D1, the controller 180 inactivates the displaying of the previewinformation 22 b. In addition, when the distance between the pointer andthe touch screen 151 is reduced to D0, that is, when the photographbutton 22 a displayed on the touch screen 151 is directly contacted andtouched, the controller 180 executes an inherent function mapped to thephotograph button 22 a.

The controller 180 may display preview information of a previous channelor a next channel relative to a channel that is currently being receivedwhen a specific region is proximity-touched while the mobile terminal100 is operating in a broadcast receiving mode. The preview informationof the previous channel or the next channel may be schedule informationacquired from a preview image of broadcasting content that is currentlybeing broadcasted through a corresponding channel or an electronicprogram guide (EPG). In the former situation, the controller 180receives broadcasting content of a previous channel or a next channel inthe background during the reception of broadcasting content through acurrent channel. When a user requests a display of preview information,the controller 180 displays a preview image of the received broadcastingcontent. In the latter situation, the controller 180 receives EPGinformation of a previous channel or a next channel in the backgroundduring the reception of broadcasting content through a current channel.When a user requests a display of preview information, the controller180 displays a broadcasting schedule using the received EPG informationon the screen.

Referring to FIG. 23A, the controller 180 displays a broadcast receivingscreen 23 on the screen when the mobile terminal 100 enters a broadcastreceiving mode. When a specific region of the broadcast receiving screen23, for example, a region where a channel changing button 23 a isdisplayed is proximity-touched, the controller 180 displays previewinformation 23 b of a channel previous to or next to the currentchannel. For example, when a channel changing button 23 a for requestinga change to a previous channel (e.g., the lower pointer of changingbutton 23 a) is proximity-touched, the controller 180 may displaypreview information of the previous channel on the screen. In addition,when the channel changing button 23 a for requesting a change to a nextchannel (e.g., the upper pointer of changing button 23 a) isproximity-touched, the controller 180 may display preview information ofthe next channel on the screen.

The controller 180 may activate or inactivate the displaying of previewinformation according to the proximity touch depth with respect to thechannel changing button 23 a. For example, referring to FIG. 23B, when aproximity depth at which the channel changing button 23 a isproximity-touched is less than a predetermined distance, the controller180 inactivates the displaying of the preview information 23 b that wasdisplayed earlier. Referring to FIG. 23C, when the channel changingbutton 23 a is contacted and touched, the controller 180 executes achannel changing function, which is an inherent function mapped (orcorresponding) to the channel changing button 23 a. That is, thecontroller 180 displays broadcasting content received for the previouschannel or the next channel on the broadcast receiving screen 23.

For example, referring back to FIG. 4, the controller 180 activates thedisplaying of the preview information 23 b when a distance between apointer causing the proximity touch (e.g., the user's finger) and thetouch screen 151 is within a range from D1 to D3. When a distancebetween the pointer and the touch screen 151 becomes shorter than D1,the controller 180 inactivates the displaying of the preview information23 b. In addition, when a distance between the pointer and the touchscreen 151 is reduced to DO, that is, when the channel changing button23 a displayed on the touch screen 151 is directly contacted andtouched, the controller 180 executes an inherent function mapped to thechannel changing button 23 a.

The controller 180 may display preview information of a web page linkedto a specific region when the specific region is touched during thedisplaying of a web page through a web browser.

Referring to FIG. 24A, the controller 180 displays a web page P1 througha web browser on the screen. An item linking to another web page P2 islocated in a region 24 a of the web page P1. When the region 24 a isproximity-touched, the controller 180 displays preview information 24 bof the web page P2 (see, e.g., FIG. 24D) linked to the correspondingregion. For example, the controller 180 displays a portion (e.g., animage) of the web page P2 linked to the region that is proximity-touchedas preview information 24 b.

The controller 180 may activate or inactivate the displaying of thepreview information 24 b according to the proximity-touch depth withrespect to the item 24 a to which the web page P2 is linked. Forexample, referring to FIG. 24B, when the proximity depth where the item24 a is proximity-touched is shorter than a predetermined distance, thecontroller 180 inactivates the displaying of the preview information 24b that was displayed earlier. Referring to FIG. 24C, when the item 24 ais contacted and touched, the controller 180 accesses the web page P2linked to the corresponding item 24 a. Referring to FIG. 24D, thecontroller 180 displays the corresponding web page P2 on the screen.

For example, referring back to FIG. 4, when a distance between a pointercausing the proximity touch (e.g., the user's finger) and the touchscreen 151 is within a range from D1 to D3, the controller 180 activatesthe displaying of the preview information 24 b. When a distance betweenthe pointer and the touch screen 151 becomes shorter than D1, thecontroller 180 inactivates the displaying of the preview information 24b. In addition, when a distance between the pointer and the touch screen151 is reduced to D0, that is, when the item 24 a displayed on the touchscreen 151 is directly contacted and touched, the controller 180displays the web page P2 linked to the corresponding item 24 a on theentire screen.

According to another embodiment of the present invention, it is possiblefor a user to check (in advance) a missed call, a missed message, andtoday's schedule by proximity-touching the corresponding alarminformation without ending the lock screen state. In addition, a usermay check (in advance) a written message in a message writing screenbefore transmission of the written message and may then send the writtenmessage. Also, a user may check (in advance) a photographed image in aphotographing screen without switching screens. Also, a user may check(in advance) broadcasting content of another channel and may then selecta desired channel. Moreover, a user may check content of a linked webpage without (fully) accessing the linked web page.

Hereinafter, a method of controlling a mobile terminal 100 according toanother embodiment of the present invention and operation of the mobileterminal 100 performing the control method will be described in moredetail with reference to FIGS. 25, 26A, 26B, 27A, 27B, 28A, 28B,29A-29C, 30A, 30B and 31A-31D.

FIG. 25 is a flowchart illustrating a control method of the mobileterminal 100 according to still another embodiment of the presentinvention. FIGS. 26A, 26B, 27A, 27B, 28A, 28B, 29A-29C, 30A, 30B and31A-31D are views illustrating a control method of the mobile terminal100 according to still another embodiment of the present invention.

Referring to FIG. 25, the controller 180 receives a proximity touchinput (e.g., via detection of a particular pressure) through the touchscreen 151 (S1601). The controller 180 determines whether there ishistory information corresponding to a proximity-touched region (S1602).If such information exists, the controller 180 displays thecorresponding history information on the touch screen 151 (S1603).

In the operation of S1603, different parts of the history informationmay be selected based on the operation mode of the mobile terminal 100,a function of an application that is being executed currently, and anitem displayed in the proximity-touched region.

FIGS. 26A, 26B, 27A, 27B, 28A, 28B, 29A-29C, 30A, 30B and 31A-31D areviews of screen displays illustrating examples of displaying the historyinformation in the mobile terminal 100 according to various embodiments.

When contact information displayed on the screen is proximity-touched,the controller 180 may display history information of a task that wasperformed previously (e.g., recently) using the proximity-touchedcontact information. Referring to FIG. 26A, the controller 180 displaysa contact screen 26 on the touch screen 151. Referring to FIG. 26B, whenspecific contact information 26 a is proximity-touched on the contactscreen 26, the controller 180 displays history information 26 b relatedto a task performed recently using the contact information 26 a that isproximity-touched.

For example, when a call to/from the contact of contact information 26 ahas occurred recently, the controller 180 may display call history ordetail information of the corresponding call as the history information26 b using the proximity-touched contact information 26 a on the screen.In addition, when a message to/from the contact has been transmittedrecently, the controller 180 may display history of the messagetransmission or detail information of a corresponding message (see,e.g., FIG. 26B) as the history information 26 b using theproximity-touched contact information 26 a on the screen. The historyinformation may be displayed such that it overlaps with the contactscreen 26 in the form of a pop-up window, or it may be displayed in asemi-transparent manner. Also, the history information may be displayedin response to only receipt (e.g., detection) of the proximity-touchinput in a particular region.

When receiver information (information regarding an intended recipient)is proximity-touched on a message writing screen, the controller 180 maydisplay history information of a message that was received recently inassociation with the proximity-touched receiver information on thescreen. Referring to FIG. 27A, the controller 180 displays a messagewriting screen 27 on the touch screen 151. Receiver information 27 a isalso displayed. Referring to FIG. 27B, when the receiver information 27a is proximity-touched on the message writing screen 27, the controller180 displays a message that was received recently in association withthe receiver information 27 a as the history information 27 b on thescreen. The history information may be displayed such that it overlapswith the message writing screen 27 in the form of a pop-up window, or itmay be displayed in a semi-transparent manner. In addition, the historyinformation may be displayed in response to only receipt (e.g.,detection) of the proximity-touch input in a particular region.

When a specific region is proximity-touched on a web browser screen, thecontroller 180 may display history information regarding web pages to beaccessed using a web browser.

Referring to FIG. 28A, the controller 180 displays web page WP1 on a webbrowser screen. The web page WP1 includes an empty (or blank) region 28a. Referring to FIG. 28B, when a specific region of the web browserscreen, for example, the empty region 28 a of the web page WP1 that isbeing displayed, is proximity-touched, the controller 180 displays aportion of another web page WP2 accessed through the web browser ashistory information 28 b. For example, the controller 180 may displaythe other web page WP2 on the web page WP1 in a layered manner.

FIGS. 29A-29C, 30A and 30B are views illustrating examples of switchingweb pages using the history information described above with referenceto FIGS. 28A and 28B. Referring to FIG. 29A, when an empty region 28 a(see, e.g., FIG. 28A) of a web page WP1 that is currently displayed isproximity-touched, the controller 180 displays history information 28 busing a portion of another web page WP2 that is accessed through the webbrowser. Referring to FIG. 29B, when the web page WP2 that is displayedas the history information 28 b is dragged by the proximity-touch, thecontroller 180 changes a size of the displayed web page WP2 based on adrag path. Referring to FIG. 29C, when the web page WP2 is dragged intoa specific region farther than a predetermined distance, the controller180 ends the displaying of the history information and displays the webpage WP2 on the entire screen.

Referring to FIG. 30A, a web page WP2 that is displayed as the historyinformation 28 b is directly contact and touched. In response, referringto FIG. 30B, the controller 180 ends the displaying of the historyinformation 28 b and displays the web page WP2 on the whole screen.

Although the figures of FIGS. 28A, 28B, 29A-29C, 30A and 30B illustratethe displaying of history information by displaying web pages in alayered manner, the controller 180 may display the history informationusing reduced (e.g., shrunken) images of the respective web pages.

Referring to FIG. 31A, the controller 180 displays web page WP1 on a webbrowser screen. The web page WP1 includes an empty (or blank) region 28a. Referring to FIG. 31B, when a specific region of the web browserscreen, for example, the empty region 28 a of the web page WP1 that iscurrently displayed, is proximity-touched, the controller 180 displaysthe history information 28 b using reduced images of other web pagesWP2, WP3, WP4 that are accessed through the web browser. With referenceto FIG. 31C, one of the other web pages (e.g., WP2) that are displayedon the screen is directly contacted and touched. In response, referringto FIG. 31D, the controller 180 ends the displaying of the historyinformation 28 b and displays the web page WP2 on the entire screen.

According to still another embodiment of the present invention, it ispossible for a user to check history information related to contactinformation without selecting a menu related to the contact information.Since only the history information is displayed using the proximitytouch, the likelihood of initiating a highly undesirable action may bereduced. Since only the history information is displayed in response tothe proximity touch, inconvenience caused by displaying the historyinformation before actually performing another function on the contactscreen is minimal.

A user may check a message that was recently sent by a recipient in themessage writing screen. Therefore, while composing a message withreference to the recently received message, a user may check therecently received message in the message writing screen without closingthe message writing screen in order to check the previously receivedmessage. As a result, user convenience is enhanced.

In addition, when a specific region is proximity-touched in a webbrowser screen, the controller 180 may display history information on aweb page that was previously accessed on the screen. A user may checkweb pages that are currently being accessed only by proximity-touching aspecific region of a web browser screen. Moreover, since only thehistory information is displayed using the proximity touch, thelikelihood of unintentionally opening an undesired web page ortriggering the execution of undesired content may be reduced.

The disclosed methods of controlling the mobile terminal may be writtenas computer programs and may be implemented in digital microprocessorsthat execute the programs using a computer readable recording medium.The methods of controlling the mobile terminal may be executed throughsoftware. The software may include code segments that perform requiredtasks. Programs or code segments may also be stored in a processorreadable medium or may be transmitted according to a computer datasignal combined with a carrier through a transmission medium orcommunication network.

The computer readable recording medium may be any data storage devicethat may store data and may be read by a computer system. Examples ofthe computer readable recording medium may include read-only memory(ROM), random-access memory (RAM), CD-ROMs, DVD±ROM, DVD-RAM, magnetictapes, floppy disks, and optical data storage devices. The computerreadable recording medium may also be distributed over network coupledcomputer systems such that the computer readable code is stored andexecuted in a distributed manner.

The foregoing embodiments and features are merely exemplary in natureand are not to be construed as limiting the present invention. Thedisclosed embodiments and features may be readily applied to other typesof apparatuses. The description of the foregoing embodiments is intendedto be illustrative, and not to limit the scope of the claims. Manyalternatives, modifications, and variations will be apparent to thoseskilled in the art.

What is claimed is:
 1. A mobile terminal comprising: a touchscreen; anda controller configured to: cause the touchscreen to display a screenincluding a plurality of items; cause the touchscreen to display adetailed screen when a touch received at a first item of the pluralityof items is a first touch type, wherein the detailed screen includesdetailed amount of data associated with the first item; cause thetouchscreen to display preview information when a touch received at afirst item of the plurality of items is a second touch type, wherein thepreview information is only a partial amount of data associated with thefirst item, wherein the partial amount of data is less than the detailedamount of data of the detailed screen, wherein an area of the previewinformation is less than an area of the screen including the pluralityof items, and wherein the first touch type is different from the secondtouch type; cause the touchscreen to maintain the displaying of thepreview information while the touch of the second touch type iscontinued to be received; and cause the touchscreen to stop thedisplaying of the preview information when the touch of the second touchtype is released.
 2. The mobile terminal of claim 1, wherein thecontroller is further configured to: change a display characteristic ofthe screen while the touch of the second touch type is continued to bereceived.
 3. The mobile terminal of claim 2, wherein the controller isfurther configured to: change the display characteristic of the screenback to an initial display characteristic when the touch of the secondtouch type is released.
 4. The mobile terminal of claim 1, furthercomprising: a touch sensor configured to provide data according to atouch received at the touchscreen; wherein the controller is furtherconfigured to: recognize touch pressure of the touch of the first touchtype and touch pressure of the touch of the second touch type accordingto the data provided by the touch sensor, wherein the touch pressure ofthe touch of the first touch type and the touch pressure of the touch ofthe second touch type are different.
 5. The mobile terminal of claim 1,wherein location of the touch of the first touch type and location ofthe touch of the second touch type are substantially same.
 6. The mobileterminal of claim 1, wherein the touch of the second touch typecomprises a touch and drag input.
 7. The mobile terminal of claim 1,wherein the preview information is displayed in a pop-up window thatobscures a portion of the screen including the plurality of items. 8.The mobile terminal of claim 7, wherein the preview information in thepop-up window comprises more detailed information than informationdisplayed in screen including the first item of the plurality of items.9. The mobile terminal of claim 7, wherein a size of the pop-up windowis larger than a displayed size of first item of the plurality of items.10. The mobile terminal of claim 7, wherein the pop-up window isdisplayed using a portion of an execution screen of the first item ofthe plurality of items.
 11. The mobile terminal of claim 7, wherein asize of the pop-up window is variable according to a type, or quantity,of the preview information.
 12. The mobile terminal of claim 7, whereinthe type of the preview information comprises at least one of text orimage.
 13. The mobile terminal of claim 1, further comprising: awireless communication unit, wherein each of the plurality of itemscomprise a task that was performed previously using the wirelesscommunication unit, wherein the task include at least one call task or amessage task.
 14. The mobile terminal of claim 1, wherein the firsttouch type is a proximity touch received at the first item, and thesecond touch type is a contact touch received at the first item.
 15. Amobile terminal comprising: a touchscreen; and a controller configuredto: cause the touchscreen to display a plurality of items; cause thetouchscreen to display a detailed screen when a touch received at afirst item of the plurality of items is a first touch type, wherein thedetailed screen includes a first amount of data associated with thefirst item; cause the touchscreen to display a preview when a touchreceived at a first item of the plurality of items is a second touchtype, wherein the preview is a partial amount of data associated withthe first item, wherein the partial amount of data is less than thefirst amount of data of the detailed screen, wherein a displayed area ofthe preview is less than an area within which the plurality of items aredisplayed, and wherein the first touch type is different from the secondtouch type; cause the touchscreen to maintain the displaying of thepreview while the touch of the second touch type is continued to bereceived; and cause the touchscreen to stop the displaying of thepreview when the touch of the second touch type is no longer received.